Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chart schemas, deployer script validation, and ci integration #1045

Conversation

consideRatio
Copy link
Contributor

@consideRatio consideRatio commented Mar 2, 2022

Summary

  • Closes Define values.schema.yaml for each Helm chart we manage to validate its passed values #937 by adding values.schema.yaml files, which if converted to values.schema.json files will be recognized by the helm CLI that will validate any passed helm chart values.
  • Adds helm chart schema validation of our clusters' hubs' configuration by trialing the helm template command against the chart in question with the non-encrypted helm chart values files.
  • Closes Helm template validation in our CI/CD #279 by adding a workflow to trial our deployer scripts validate command by using the non-encrypted helm chart values files.
  • Closes basehub: ensure default values are set for all values used by templates #994 by manually ensuring and using the new schemas to ensure we don't have Helm chart values our templates rely on, but that we don't provide default values for in the Helm chart's values.yaml file
  • Cleans up helm chart configuration that wasn't correct, as identified by the schema files
  • Cleaned up logic associated with and content of requirements.txt and dev-requirements.txt
    • requirements.txt is now purely dependencies for the deployer script
    • dev-requirements.txt is now purely dependencies for scripts in the extra_scripts folder etc
    • Both files have inline comments to clarify the situation

Test failure unrelated

The test failure is unrelated and is resolved by #1044.

Comment on lines -1 to -7
scratchBucket:
# Enable a 'scratch' bucket per-hub, with read-write permissions for all
# users. This will set a `SCRATCH_BUCKET` env variable (and a PANGEO_SCRATCH variable
# too, for backwards compatibility). Users can share data with each other using
# this bucket.
enabled: true

Copy link
Contributor Author

@consideRatio consideRatio Mar 2, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This configuration section was silently ignored.

I opened #1046 to reflect removing this instead of setting it correctly in a way that would make it be respected. If I would have set this correctly, I would have potentially changed behavior etc and I didn't want to do that as part of this PR.

@sgibson91
Copy link
Member

I am going to merge this now as I'd like to use some of the functionality added in the deployer in #1047 to validate our support chart 🎉

@sgibson91 sgibson91 merged commit 60917a8 into 2i2c-org:master Mar 2, 2022
@sgibson91
Copy link
Member

I updated all the clusters/hubs helm charts locally and all is fine - so any failures in CI leftover are flakey tests

@damianavila
Copy link
Contributor

Lovely work, @consideRatio!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants